Hi @thibsy,
thanks for the feedback.

This is another good example of why the @yaiero/tagify library keeps causing friction. We repeatedly work around some issues or limitations to bend this library to all our needs, which keeps trading one problem for another and adds much unnecessary complexity. We should get rid of this library short-term.

I agree, AFAIK we also just need a fraction of the functionality the library provides.

Isn't there an existing element that supports all attributes the library needs? Maybe even an (although this might be tricky due to name etc.)?

The ui-tag-input can be replaced with a button element, in terms of attribute and sematic context (but with some custom CSS). I will update the PR.
But not the other two:
The ui-tag-dropdown-item requires the attribute tagifySuggestionIdx which is invalid for all existing HTML elements and the ui-tags-input requires attributes like readonly, disabled but also children, for which I could not find any matching elements.

If I remember correctly, we originally moved to a div because the custom HTML tag of the library was flagged during an A11Y inspection or some HTML-validator run (not entirely sure though). Would we not simply cause this issue again, since we embed a custom HTML tag of our own?

No, because the problem with the tagify library is that they don't use valid custom elements.
Custom HTML elements MUST contain a dash (-) (https://html.spec.whatwg.org/multipage/custom-elements.html#valid-custom-element-name).
The tagify library simply uses <tags> etc. which is invalid.

If I read this correctly they don't need to be defined with window.customElements.define(...) but it is best practice, so I added it (https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements).

I also tested the custom elements with the W3C HTML Validator which was used for the failed TestRail Cases (at least for the linked Mantis Issues). No issues are reported with the custom elements (with a dash) + attributes.

Best regards
@lscharmer

Hi @lscharmer,

Thx a lot for the explanation. I was not aware of how custom HTML tags work exactly. From my POV there is no need to replace the one tag with a button then. I want as little overhead as possible. You could even remove the tags registration then, since its optional.

Let me know if I should integrate this as is.

Kind regards,
@thibsy (as UI coordinator)